Avoid computing lazy scalar coordinates when printing a Cube#5788
Closed
fnattino wants to merge 1 commit intoSciTools:mainfrom
Closed
Avoid computing lazy scalar coordinates when printing a Cube#5788fnattino wants to merge 1 commit intoSciTools:mainfrom
fnattino wants to merge 1 commit intoSciTools:mainfrom
Conversation
Member
|
Note: we are planning now a minor "interim" release to include #5833 and #5740 Status : I think ..
|
Member
|
@fnattino if it's ok with you, I'm going to take this + add a couple of commits to fix + extend the testing slightly. |
Contributor
tomorrow* |
Contributor
|
Completed in #5896 . |
Contributor
Author
Member
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚀 Pull Request
Description
The point and bound of a scalar coordinate are printed out only when the corresponding data is not lazy. Fix #5743.
Consult Iris pull request check list